|
The Zachman Framework is an enterprise ontology and is a fundamental structure for Enterprise Architecture which provides a formal and structured way of viewing and defining an enterprise. The ontology is a two dimensional classification schema that reflects the intersection between two historical classifications. The first are primitive interrogatives: What, How, When, Who, Where, and Why. The second is derived from the philosophical concept of reification, the transformation of an abstract idea into an instantiation. The Zachman Framework reification transformations are: Identification, Definition, Representation, Specification, Configuration and Instantiation.〔John Zachman's Concise Definition of the Zachman Framework, 2008〕 The Zachman Framework is not a methodology in that it does not imply any specific method or process for collecting, managing, or using the information that it describes.;〔(【引用サイトリンク】title=The Zachman Framework: The Official Concise Definition )〕 rather, it is an ontology whereby a schema for organizing architectural artifacts (in other words, design documents, specifications, and models) is used to take into account both whom the artifact targets (for example, business owner and builder) and what particular issue (for example, data and functionality) is being addressed.〔(''A Comparison of the Top Four Enterprise Architecture Methodologies'' ), Roger Sessions, Microsoft Developer Network Architecture Center,〕 The framework is named after its creator John Zachman, who first developed the concept in the 1980s at IBM. It has been updated several times since.〔(【引用サイトリンク】title=The Zachman Framework Evolution )〕 == Overview == The title "Zachman Framework" refers to The Zachman Framework for Enterprise Architecture with version 3.0 being the most current. The Zachman Framework has evolved in its thirty year history to include: * The initial framework, named ''A Framework for Information Systems Architecture'', by John Zachman published in an 1987 article in the IBM Systems journal.〔(【引用サイトリンク】title=A framework for information systems architecture )〕 * The ''Zachman Framework for Enterprise Architecture'', an update of the 1987 original in the 1990s extended and renamed .〔The Open Group (1999–2006). ("ADM and the Zachman Framework" ) in: ''TOGAF 8.1.1 Online''. Accessed 25 Jan 2009.〕 * One of the later versions of the Zachman Framework, offered by Zachman International as industry standard. In other sources the Zachman Framework is introduced as a framework, originated by and named after John Zachman, represented in numerous ways, see image. This framework is explained as, for example: * a framework to organize and analyze data,〔William H. Inmon, John A. Zachman, Jonathan G. Geiger (1997). ''Data Stores, Data Warehousing, and the Zachman Framework: Managing Enterprise Knowledge''. McGraw-Hill, 1997. ISBN 0-07-031429-2.〕 * a framework for enterprise architecture.〔Pete Sawyer, Barbara Paech, Patrick Heymans (2007). ''Requirements Engineering: Foundation for Software Quality''. page 191.〕 * a classification system, or classification scheme〔Kathleen B. Hass (2007). ''The Business Analyst as Strategist: Translating Business Strategies Into Valuable Solutions''. page 58.〕 * a matrix, often in a 6x6 matrix format * a two-dimensional model〔Harold F. Tipton, Micki Krause (2008). ''Information Security Management Handbook, Sixth Edition, Volume 2''. page 263.〕 or an analytic model. * a two-dimensional schema, used to organize the detailed representations of the enterprise.〔O'Rourke, Fishman, Selkow (2003). ''Enterprise Architecture Using the Zachman Framework''. page 9.〕 Beside the frameworks developed by John Zachman, numerous extensions and/or applications have been developed, which are also sometimes called Zachman Frameworks, however they generally tend to be graphical overlays of the actual framework itself. The Zachman Framework summarizes a collection of perspectives involved in enterprise architecture. These perspectives are represented in a two-dimensional matrix that defines along the rows the type of stakeholders and with the columns the aspects of the architecture. The framework does not define a methodology for an architecture. Rather, the matrix is a template that must be filled in by the goals/rules, processes, material, roles, locations, and events specifically required by the organization. Further modeling by mapping between columns in the framework identifies gaps in the documented state of the organization.〔James McGovern et al. (2003). ''A Practical Guide to Enterprise Architecture''. p. 127-129.〕 The framework is a logical structure for classifying and organizing the descriptive representations of an enterprise. It is significant to both the management of the enterprise, and the actors involved in the development of enterprise systems.〔Marc Lankhorst et al. (2005). ''Enterprise Architecture at Work''. p. 24.〕 While there is no order of priority for the columns of the Framework, the top-down order of the rows is significant to the alignment of business concepts and the actual physical enterprise. The level of detail in the Framework is a function of each cell (and not the rows). When done by IT the lower level of focus is on information technology, however it can apply equally to physical material (ball valves, piping, transformers, fuse boxes for example) and the associated physical processes, roles, locations etc. related to those items. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Zachman Framework」の詳細全文を読む スポンサード リンク
|